Precision
| Characteristic Name: | Precision |
| Dimension: | Accuracy |
| Description: | Attribute values should be accurate as per linguistics and granularity |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of tasks failed or under performed due to lack of data precision |
| The number of complaints received due to lack of data precision |
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Ensure the data values are correct to the right level of detail or granularity | (1) Price to the penny or weight to the nearest tenth of a gram. (2) precision of the values of an attribute according to some general-purpose IS-A ontology such as WordNet |
| Ensure that data is legitimate or valid according to some stable reference source like dictionary/thesaurus/code. | (1) Spellings and syntax of a description is correct as per the dictionary/thesaurus/Code (e.g. NYSIIS Code) (2) Address is consistent with global address book |
| Ensure that the user interfaces provide the precision required by the task | (1) if the domain is infinite (the rational numbers, for example), then no string format of finite length can represent all possible values. |
| Ensure the data values are lexically, syntactically and semantically correct | (1) “Germany is an African country” (semantically wrong); Book.title: ‘De la Mancha Don Quixote’ (syntactically wrong); UK’s Prime Minister: ‘Toni Blair’ (lexically wrong) |
Validation Metric:
| How mature is the creation and implementation of the DQ rules to maintain data precesion |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| if v = Jack,even if v = John, v is considered syntactically correct, as Jack is an admissible value in the domain of persons’ names | C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Data values are correct to the right level of detail or granularity, such as price to the penny or weight to the nearest tenth of a gram. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| Data is correct if it conveys a lexically, syntactically and semantically correct statement – e.g.,the following pieces of information are not correct:“Germany is an African country” (semantically wrong);Book.title: ‘De la Mancha Don Quixote’ (syntactically wrong); UK’s Prime Minister: ‘Toni Blair’ (lexically wrong). | KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published. |
| The set S should be sufficiently precise to distinguish among elements in the domain that must be distinguished by users. This dimension makes clear why icons and colors are of limited use when domains are large. But problems can and do arise for the other formats as well, because many formats are not one-to-one functions. For example, if the domain is infinite (the rational numbers, for example), then no string format of finite length can represent all possible values. The trick is to provide the precision to meet user needs. | LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub. |
| Is the information to the point, void of unnecessary elements? | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. |
| The degree of precision of the presentation of an attribute’s value should reasonably match the degree of precision of the value being displayed. The user should be able to see any value the attributer may take and also be able to distinguish different values. | REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc. |
| The granularity or precision of the model or content values of an information object according to some general-purpose IS-A ontology such as WordNet. | STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |
Appropriate presentation
| Characteristic Name: | Appropriate presentation |
| Dimension: | Usability and Interpretability |
| Description: | The data presentation is aligned with its use |
| Granularity: | Information object |
| Implementation Type: | Process-based approach |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to the lack of appropriate presentation of data |
| The number of complaints received due to the lack of appropriate presentation of data |
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Ensure that Universally accepted standard formats are used to maintain the compatibility of information across organisations and across time | (1) A patients diagnostic card generated in one hospital is compatible with another hospital. |
| Ensure that information can be aggregated or combined through the use of compatible formats | (1) Product wise monthly sales report can be generated by combining the sales reports of three subsidiaries |
| Ensure that the data presentations are familiar to the users even if the application platform is changed. | (1) A quotation created in one system is sent to another system through an EDI message and displayed in the same presentation format |
| Ensure the media of presentation is appropriate for the target group | (1) A step by step written instruction list in a documents appropriate for a software engineer. (2) A video display is appropriate for a mechanic |
| Ensure that the presentation formats are flexible to accommodate changes easily | (1) An invoice document may require additional space to mansion authorisation evidence |
Validation Metric:
| How mature is the process to maintain appropriate presentation of data |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| my birth date is December 13, 1941. If a personnel database has a BIRTH_DATE data element that expects dates in USA format, a date of 12/13/1941 would be correct. A date of 12/14/1941 would be inaccurate because it is the wrong value. A date of 13/12/1941 would be wrong because it is a European representation instead of a USA representation. | J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| A measure of how information is presented to and collected from those who utilize it. Format and appearance support appropriate use of information. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| 1) The Characteristic in which formatted data is presented consistently in a standardized or consistent way across different media, such as in computer screens, reports, or manually prepared reports.
2) The Characteristic of Information being presented in the right technology Media, such as online, hardcopy report, audio, or video. 3) The degree to which Information is presented in a way Intuitive and appropriate for the task at hand. The Presentation Quality of Information will vary by the individual purposes for which it is required. Some users require concise presentation, whereas others require a complete, detailed presentation, and yet others require graphic, color, or other highlighting techniques. |
ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
| 1) Appropriateness is the dimension we use to categorize how well the format and presentation of the data match the user needs. In our example, there is a difference between a high-level monthly sales report that is supplied to senior management and the daily product manifests that are handed to the shipping department for product packaging.
2) Flexibility in presentation describes the ability of the system to adapt to changes in both the represented information and in user requirements for presentation of information. For example, a system that display different counties; currencies may need to have the screen presentation change to allow for more significant digits for prices to be displayed when there is a steep devaluation in one county’s currency. 3) In an environment that makes use of different kinds of systems and applications, a portable interface is important so that as applications are migrated from one platform to another, the presentation of data is familiar to the users. Also, when dealing with a system designed for international use, the user of international standards as well as universally recognized icons is a sign of system designed with presentation portability in mind. |
LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub. |
| 1) Data is presented in an intelligible manner.
2) Data is presented in a manner appropriate for its use, with respect to format, precision, and units. |
PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
| Good format, like good views, are flexible so that changes in user need and recording medium can be accommodated. | REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc. |
| Data are always presented in the same format and are compatible with the previous data. | WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33. |